fix joins for missing key columns#187
Merged
mchav merged 9 commits intoDataHaskell:mainfrom Mar 25, 2026
Merged
Conversation
Contributor
Author
|
@daikonradish @mchav, can you review this pr? |
mchav
requested changes
Mar 20, 2026
Contributor
|
We've left some comments, but in general your code looks good. Some of it is very stylish! Thank you for your effort. |
Contributor
Author
|
@mchav @daikonradish fixed all the issues. check once? |
mchav
requested changes
Mar 21, 2026
Contributor
Author
|
@mchav check now? |
mchav
requested changes
Mar 23, 2026
be407f8 to
8d3d381
Compare
8d3d381 to
b740b06
Compare
Contributor
Author
|
@mchav check now? |
Member
|
Thank you @Anamika1608 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #118
summary
this fixes the join behavior when a requested join key does not exist. instead of silently hashing an empty key set and producing cartesian style output, joins now fail fast with the existing columnnotfoundexception.
what changed
behavior
before this change, a missing join column could fall through to hashing zero key columns, which made every row hash the same and could expand into cartesian style output. after this change, the join fails immediately with the missing column name and the existing available column context.
verification